<!--$Id: ex.so,v 1.8 2006/10/05 01:06:08 bostic Exp $-->
<!--Copyright (c) 1997,2008 Oracle.  All rights reserved.-->
<!--See the file LICENSE for redistribution information.-->
<html>
<head>
<title>Berkeley DB Reference Guide: Ex_rep: a replication example</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<table width="100%"><tr valign=top>
<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Berkeley DB Replication</dl></b></td>
<td align=right><a href="../rep/faq.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../rep/ex_comm.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p align=center><b>Ex_rep: a replication example</b></p>
<p>Ex_rep, found in the <b>examples_c/ex_rep</b> subdirectory
of the Berkeley DB distribution, is a simple but complete demonstration of a
replicated application.  The application is a mock stock ticker.  The
master accepts a stock symbol and an numerical value as input, and
stores this information into a replicated database; either master or
clients can display the contents of the database, given an empty input
line.</p>
<p>There are two versions of the application: ex_rep_mgr uses Replication
Manager, while ex_rep_base uses the Base replication API.  This is
intended to demonstrate that, while the basic function of the
application is the same in either case, the replication support
infrastructure differs markedly.</p>
<p>The communication infrastructure demonstrated with ex_rep_base has the
same dependencies on system networking and threading support as does
the Replication Manager (see the <a href="../../ref/rep/intro.html">Introduction</a>).  The Makefile created by the standard UNIX
configuration will build the ex_rep examples on most platforms.  Enter
"make ex_rep_mgr" and/or "make ex_rep_base" to attempt to build
them.</p>
<p>The synopsis for both programs is as follows:</p>
<pre>ex_rep_xxx [<b>-MC</b>] [<b>-h home</b>] [<b>-m host:port</b>] [<b>-o host:port</b>] [<b>-n sites</b>] [<b>-p priority</b>]</pre>
<p>where "ex_rep_xxx" is either "ex_rep_mgr" or "ex_rep_base".</p>
<p>The options, to either version of the program, are as follows:</p>
<br>
<b>-M</b><ul compact><li>Configure this process as a master.</ul>
<b>-C</b><ul compact><li>Configure this process as a client.</ul>
<b>-h</b><ul compact><li>Specify a home directory for the database environment; by
default, the current working directory is used.</ul>
<b>-m</b><ul compact><li>Listen on port "port" of host "host" for incoming connections.</ul>
<b>-o</b><ul compact><li>Attempt to connect to another member of the replication group which is
listening on host "host" at port "port".  Members of a replication group
should be able to find all other members of a replication group so long
as they are in contact with at least one other member of the replication
group.</ul>
<b>-n</b><ul compact><li>Specify the total number of sites in the replication group.</ul>
<b>-p</b><ul compact><li>Set the election priority.  See <a href="../../api_c/rep_elect.html">DB_ENV-&gt;rep_elect</a> for more
information.</ul>
<br>
<p>A typical ex_rep session begins with a command such as the
following, to start a master:</p>
<blockquote><pre>ex_rep_mgr -M -p 100 -n 4 -h DIR1 -m localhost:6000</pre></blockquote>
<p>and several clients:</p>
<blockquote><pre>ex_rep_mgr -C -p 50 -n 4 -h DIR2 -m localhost:6001 -o localhost:6000
ex_rep_mgr -C -p 10 -n 4 -h DIR3 -m localhost:6002 -o localhost:6000
ex_rep_mgr -C -p  0 -n 4 -h DIR4 -m localhost:6003 -o localhost:6000</pre></blockquote>
<p>In this example, the client with home directory DIR4 can never become
a master (its priority is 0).  Both of the other clients can become
masters, but the one with home directory DIR2 is preferred.  Priorities
are assigned by the application and should reflect the desirability of
having particular clients take over as master in the case that the
master fails.</p>
<table width="100%"><tr><td><br></td><td align=right><a href="../rep/faq.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../rep/ex_comm.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p><font size=1>Copyright (c) 1996,2008 Oracle.  All rights reserved.</font>
</body>
</html>
